Pin the Unraid template to 0.15.2 - #471
Merged
Merged
Conversation
Community Applications serves the template from main, so Unraid installs were sitting on 0.15.1 while 0.15.2 was the current release. Worth being plain about the size of this: for a container 0.15.1 and 0.15.2 are near enough the same software. The only change between them that reaches Docker is one extra field in the /api/health payload. The rest of 0.15.2 is the Rust desktop shell, which containers never ship. So this buys Unraid users nothing functional today. It buys version identity, which is what #453 was about. A bug report from Unraid names whatever the template handed out, and a pin that habitually lags makes every report need translating first. It also stops the gap compounding into a catch-up bump that changes several things at once. Confirmed the image exists before pinning: Docker Publish succeeded on the release event for v0.15.2. An anonymous ghcr manifest check is not evidence either way here, 0.15.1 and latest 404 on the same query.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #470
One line:
ghcr.io/stemdeckapp/stemdeck:0.15.1becomes:0.15.2.What this actually gives Unraid users
Very little, and it is better to say so than to imply otherwise. For a container, 0.15.1 and 0.15.2 are near enough the same software:
The only part of that reaching Docker is one extra field in the
/api/healthpayload.desktop/src-tauri/src/main.rsis the bulk of the change and containers never ship it.What it does give is version identity, the same thing #453 was about. An Unraid bug report names whatever the template handed out, and a pin that habitually lags means every report needs translating before it can be acted on. Letting the gap grow also turns the eventual bump into several changes landing at once, none of them individually observed in the container path.
The image exists
Checked before pinning, since a pin to an unpublished tag is an immediate pull failure for every Unraid user and Community Applications serves this file from
mainlive.Docker Publishsucceeded on thereleaseevent forv0.15.2. Worth noting for anyone repeating the check: an anonymous GHCR manifest request is not evidence here either way, because0.15.1andlatestreturn 404 on the same query despite both existing.XML still parses.